|
Misuse Case is a business process modeling tool used in the software development industry. The term ''Misuse Case'' or ''mis-use case'' is derived from and is the inverse of use case.〔Sindre and Opdahl (2001). "(Capturing Security Requirements through Misuse Cases )"〕 The term was first used in the 1990s by Guttorm Sindre of the Norwegian University of Science and Technology, and Andreas L. Opdahl of the University of Bergen, Norway. It describes the process of executing a malicious act against a system, while use case can be used to describe any action taken by the system .〔Sindre and Opdahl (2004). "(Eliciting security requirements with misuse cases )"〕 == Overview == Use cases specify required behaviour of software and other products under development, and are essentially structured stories or scenarios detailing the normal behavior and usage of the software. A Misuse Case on the other hand highlights something that should not happen (i.e. a Negative Scenario) and the threats hence identified, help in defining new requirements, which are expressed as new Use Cases. This modeling tool has several strengths: * It allows you to provide equal weightage to functional and non-functional requirements (e.g. security requirements, platform requirements, etc.), which may not be possible with other tools. * It makes you focus on security from the beginning of the design process and it allows you to avoid premature design decisions. * It is a very good tool for improving communication between developers and stakeholders and is valuable in ensuring that both agree on critical system solutions and Trade-off analysis.〔(Initial Industrial Experience of Misuse Cases in Trade-Off Analysis (2002, by Ian Alexander) )〕 * Creating misuse cases often trigger a chain reaction which eases the identification of functional and non-functional requirements. The discovery of a misuse case will often leads to the creation of a new use case which acts as a counter measure. This in turn might be the subject of a new misuse case.〔(Misuse cases help to elicit non-functional requirements (2003, by Ian Alexander) )〕 * As compared to other tools, It relates better to use cases and UML and eases the seamless employment of the model. Its biggest weakness is its simplicity. It needs to be combined with more powerful tools to establish an adequate plan for the execution of a project.〔 One other weakness is its lack of structure and semantics. 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「Misuse case」の詳細全文を読む スポンサード リンク
|